|
|
BT_Music.mp4 (3,820,248 bytes) |
|
|
Hello, Sam, SKB QA engineer report this issue. https://jira.skbroadband.com/browse/BPM-29401 Sometimes the key event got as repeat event, but I didn't press as long. // NOT REPEAT KEY 06-18 16:58:06.431 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:06.625 726 900 D WindowManager interceptKeyTi keyCode=166 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null // NOT REPEAT KEY 06-18 16:58:08.082 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:08.087 726 900 D WindowManager interceptKeyTi keyCode=166 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null // NOT REPEAT KEY 06-18 16:58:09.561 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:09.602 726 900 D WindowManager interceptKeyTi keyCode=166 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null // REPEAT KEY !!!! 06-18 16:58:10.650 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.150 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=1 keyguardOn=false canceled=false policyFlags=1107296256 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.199 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=2 keyguardOn=false canceled=false policyFlags=1107296256 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.274 726 900 D WindowManager interceptKeyTi keyCode=166 down=true repeatCount=3 keyguardOn=false canceled=false policyFlags=1107296256 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.296 726 900 D WindowManager interceptKeyTi keyCode=166 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null This issue only can be reproduced if you using BT RCU under music is playing through bluetooth. Could you please check it? Thank you. Sangmin Choi. |
|
|
Hi Mr. Sangmin Choi, From the timestamp, it looks like system is too busy to handle key events. 'skbrm_raw_event' is printed while kernel receives a key event. From log below, the down/up delta time is about 600ms, so Android Frameworks handle it as a repeat key. [ 892.109943] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 40 00 [ 892.747628] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 ff ff To identify CPU or BT related issue, you may need to get CPU usage and BT snoop log. Thanks. 06-18 16:58:10.650 2096 2128 D kernel : <4>[ 892.109943] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 40 00 06-18 16:58:10.650 726 900 D WindowManager: interceptKeyTi keyCode=166 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:10.650 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:11.150 726 900 D WindowManager: interceptKeyTi keyCode=166 down=true repeatCount=1 keyguardOn=false canceled=false policyFlags=1107296256 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.150 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:11.199 726 900 D WindowManager: interceptKeyTi keyCode=166 down=true repeatCount=2 keyguardOn=false canceled=false policyFlags=1107296256 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.200 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:11.274 726 900 D WindowManager: interceptKeyTi keyCode=166 down=true repeatCount=3 keyguardOn=false canceled=false policyFlags=1107296256 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:11.274 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:11.295 2096 2128 D kernel : <4>[ 892.747628] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 ff ff 06-18 16:58:11.296 726 900 D WindowManager: interceptKeyTi keyCode=166 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=402 mCharacters=null 06-18 16:58:14.181 726 900 D WindowManager: interceptKeyTi keyCode=14 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=8 mCharacters=null 06-18 16:58:14.181 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:14.185 2096 2128 D kernel : <4>[ 895.640690] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 27 00 06-18 16:58:14.282 726 900 D WindowManager: interceptKeyTi keyCode=14 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=8 mCharacters=null 06-18 16:58:14.283 726 900 D WindowManager: interceptKeyTi keyCode=11 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=5 mCharacters=null 06-18 16:58:14.283 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:14.285 2096 2128 D kernel : <4>[ 895.741754] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 ff ff 06-18 16:58:14.285 2096 2128 D kernel : <4>[ 895.741996] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 24 00 06-18 16:58:14.285 2096 2128 D kernel : <4>[ 895.742076] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 ff ff 06-18 16:58:14.287 726 900 D WindowManager: interceptKeyTi keyCode=11 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=5 mCharacters=null 06-18 16:58:16.021 2096 2128 D kernel : <4>[ 897.481320] --> skbrm_raw_event: id=0x03, size=5, data= 03 41 00 00 00 06-18 16:58:16.021 2096 2128 D kernel : <4>[ 897.482348] --> skbrm_raw_event: id=0x03, size=5, data= 03 00 00 00 00 06-18 16:58:16.022 726 900 D WindowManager: interceptKeyTi keyCode=23 down=true repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=232 mCharacters=null 06-18 16:58:16.022 726 900 D WindowManager: interceptKeyTi strDate 2024-06-18 16:58 06-18 16:58:16.025 726 900 D WindowManager: interceptKeyTi keyCode=23 down=false repeatCount=0 keyguardOn=false canceled=false policyFlags=1644167168 mDeviceId=4 mSource=1793 mScanCode=232 mCharacters=null |
|
|
Hello, Kerwin, Did you reproduce this issue? What is the next step of this issue? Thank you. Sangmin Choi. |
|
|
Hi Mr. Sangmin Choi, Current, Sam has trouble to login and access SKB HOME UI on his SWAN device. He still tries on other devices. So we don't reproduce this issue yet. Thanks. |
|
|
Hi Sangmin, I am trying to reproducing it, thanks~ Sam |
|
|
Hi Sangmin, After test many times, when the issue occurs, I find that in btsnoop log the RCU down/up signals are not delay. So, the cause is that the RCU up signal is handled delayed by the system. Then the kernel handles delayed("kernel : <4>[ 892.747628] --> skbrm_raw_event: id=0x80, size=4, data= 80 00 ff ff"). The provement: From "btsnoop_20240710_rcuKeyAbnrmllyRepeat3.PNG" logcat log, you can see the RCU up signal is delay(... 17:34.608 ... interceptKeyTi keyCode=167 down=false...). And from "btsnoop_hci.cfa" & "btsnoop_20240710_rcuKeyAbnrmllyRepeat4.PNG", you can see the RCU up signal is not delay(... 17:34.044036). Please let Synaptics to check this issue and help to analyze the root cause. Thanks~ Sam btsnoop_20240710_rcuKeyAbnrmllyRepeat3.PNG (98,659 bytes) btsnoop_20240710_rcuKeyAbnrmllyRepeat4.PNG (35,379 bytes) |
|
|
Hello, Sam, I created the Synaptics ticket. https://synacsm.atlassian.net/servicedesk/customer/portal/173/CSMSKBSBLT-244 Thank you. Sangmin Choi. |
|
|
Hi Sam, Do you have any update for this issue ? |
|
|
Hi Wooshin, From btsnoop log, the RCU down/up signals are not delay. So we think it's CPU delay for handling RCU signal. We need Synaptics to analyze the root cause. Thanks~ Sam |
|
|
Hi Sam, I know about that, and already inform it to Synaptics. To get feedback in short time, need to push Synaptics. Please push them. Thanks. |
|
|
Hi Wooshin, Already pushed them, thanks~ Sam |
|
|
Hello, Sam, There is a feedback from Synaptics. https://synacsm.atlassian.net/servicedesk/customer/portal/173/CSMSKBSBLT-244 Could you please contact with Allen Wang at the CSMSKBSBLT-244 directly ? Thank you. Sangmin Choi. |
|
|
스크린샷 2024-11-04 오전 9.31.20.png (68,715 bytes) |
|
|
Hello, Sam, Could you please let me know the status of this issue? Thank you. Sangmin Choi. |
|
|
Hi Mr. Sangmin Choi, Please recall updates from Sam. (https://btracker-cns.fii-foxconn.com/vaas/view.php?id=1963#c16239) This issue is not related to RTK BT or BT stack. That's why we need ask help from Synaptics. Thanks! |
|
|
Hello, Kerwin, Please contact with Allen Weng directly at https://synacsm.atlassian.net/servicedesk/customer/portal/173/CSMSKBSBLT-244. Thank you. Sangmin Choi. |
- yk.jung ( (ALTech) Younkwang Jung ) developer
